Intel RSTe(Rapid Storage Technology enterprise) RAID Driver for Windows 2022/2019 Supported Controllers: Intel VROC (SATA RAID) NOTE TO SERVICE - Reference RETAIN #N/A Version 8.5.0.1592-0 ------------------ Fixed issue -Awhile adding a disk, it may not be added to the existing Raid 0, and an "Internal error" message may also be returned.(18033850568) -The trial notification at the start of the trial may display 0 days instead of 90.(18033876218) -Data could be corrupted on raid 5 under specific conditions.This has been addressed in a technical advisory that can be provided by Intel.(18033689418) -With a SATA RAID 5, there may be an OS System Hang 72 during the period when a system enters into S4 hibernate state.(18025836360) -Smart App Control could block Intel® VROC driver actions.(18031491855) -Enable Intel® VMD may increase boot time by 15 sec without a hardware key plugged in.(15012158141) -Rebuild action may be very slow with some cache settings set incorrectly.(18022848256) -Migrating volume to another level may be impossible when user changes the name of volume.(18023073780) -Missing disk used to have ID 0-255-0-0 after reboot.(14019194649) -Event ID 4155 regarding CD/DVD rom used to show invalid serial number of the device.(15012777627) -The SATA RAID 1 rebuild speed was slower than expected which was fixed from very slow rebuild speeds from baseline, to what it should be at.(15012986924) -Operation" property may not show ongoing rebuild process.(15014295238) -When attempting to rebuild a degraded RAID 10 matrix (second RAID volume is a RAID 5) with 2 drive failures (RAID 10 - Degraded; RAID 5 - Fail), the Intel® VROC driver may become unresponsive.(18015582447) -Intel® VROC Bad Block Management (BBM) logging may report the wrong drive serial number when logging BBM events..(18023331378) Version 8.0.7.1003 ------------------ -Exceptional boot delay with WD Gold HDD used as SATA data drive attached to RAID mode port, but not in a RAID volume.(14014436257) Version 8.0.0.4028 ------------------ -A second RAID volume may not rebuild to the hot-spare drive after resetting one member disk to non-RAID.(1508749788) -Hot removal of a matrix RAID member may result in a system failure.(1508747791) -When running in a matrix RAID configuration (two RAID volumes in a single RAID array), the bad block management process may not properly detect bad blocks..(18013439721) -System may fail to start after an unexpected power loss..(1806564424) Version 7.7.0.1260 ------------------ -Intel® VROC bad block management process may take (3 to 4 times) longer than in previous versions.(18016058101) -[VROC] Drive failure messages seen on initiating IO.(1508906750) -Performing an Intel® VROC (SDATA RAID) RAID 5 write hole recovery on a degraded SATA RAID 5 volume may not complete successfully.(18014127243) -A potential silent data loss condition exists in both the Intel® VROC (SATA RAID) and the Intel® RSTe Windows-based products. The potential silent data loss condition exists when the Intel® VROC Read Patrol feature is enabled for redundant SATA RAID volumes (RAID 1, 5 or 10) and one of the RAID member drives is found to have a bad block condition. The Read Patrol process, of using the redundant data to correct the bad block, can result in invalid data being written.(22011073918) -Intel® VROC SATA/sSATA RAID volumes may degrade or fail under high I/O load if an ATA pass through command is issued.(14014598311) -Fail to install Windows* Server 2019 with QWMB CPU.(1508793548) -when running stress testing on M.2 slots managed by the sSATA controller, an isStorB error may be logged.(1507753655) -Intel® VROC may not properly calculate the LBA locations when performing the Read Patrol Bad Block Recovery process, inadvertently missing some bad blocks..(22011196948) -Intel® VROC RAID Write Hole parity calculation may be computed incorrectly..(14012886123) -System may fail to start after an unexpected power loss..(1806564424) Version 7.5.0.1990 ------------------ Initial Release -A potential silent data loss condition exists in both the Intel® VROC (SATA RAID) and the Intel® RSTe Windows-based products. The potential silent data loss condition exists when the Intel® VROC Read Patrol feature is enabled for redundant SATA RAID volumes (RAID 1, 5 or 10) and one of the RAID member drives is found to have a bad block condition. The Read Patrol process, of using the redundant data to correct the bad block, can result in invalid data being written.(22011073918) -The order of the SATA drives attached to the sSATA controller may not match that of how they may be reported in the SATA controller(14011049937) -When running stress testing on M.2 slots managed by the sSATA controller, an isStorB error may be logged. Expected under such heavy I/O loads.(1507753655)